Retire legacy execution and enforce CLI quality gates - #9
Merged
Conversation
Refresh native provider contracts, add Gemini and Antigravity integration and skill projection, preserve raw provider arguments, and expose portable MCP tool names for Google hosts.
Add safe workspace isolation, foreground and detached native launches, resume and lifecycle controls, normalized artifacts, grouped execution, and authenticated daemon routes while preserving provider-owned sessions.
Introduce ~/.rudi/outputs as the canonical artifact path, migrate legacy output contents without overwrites, remove stale compatibility links, and expose the lifecycle through home and managed instructions.
Recognize native rate_limit_event payloads, retain validated reset and overage metadata, and avoid leaking untyped provider objects into normalized artifacts.
Archive obsolete run-group and test-result documentation, replace stale testing guidance, and align the advertised info command with generic package inspection while retaining live compatibility commands.
Regenerate the published CLI bundle, package manifest, and standalone MCP router from the verified source tree.
Record the reviewed delete/extract/retain boundary and persist the phase-gated SWE compliance plan before implementation.
Run tests, reproducible builds, portable architecture debt scans, and package verification on pull requests and main. Pin the package manager and reviewed native build scripts for clean CI installs.
Make Agent Host own provider configuration, argv construction, and Claude/Codex event normalization. Leave temporary legacy re-exports only until the retired execution tree is deleted.
rudijetson
changed the title
rudijetson
marked this pull request as ready for review
August 2, 2026 17:40
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
qualityworkflow for tests, standalone builds, generated-distribution drift, changed-file debt scanning, and package contentsrudi.dbfiles/agent-host/v1OpenAPI contractArchitecture boundary
Native agent providers remain authoritative for sessions, transcripts, model loops, and provider-native orchestration. RUDI owns local capabilities, secrets, MCP integration, indexes, artifacts, safe workspaces, bounded launch lifecycle, and daemon health.
packages/dbremains isolated only for the checked-in Studio consumer; the CLI and runner do not import it.Validation
pnpm buildand generated-distribution drift checkrudi.dbcreationmainbranch protection requires strictqualitychecks and enforces them for administratorsCompatibility
There are no callable legacy execution or imported-session implementations in the CLI. Existing local data is left untouched. Retired command names remain only as explicit nonzero migration notices.